

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Software Engineers [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Project Role,Project Role Software Engineer,Software Engineer,Software Engineer Project Role,Software Engineer And Enterprise Architect,Enterprise Architect,Enterprise Architect For Software Engineers">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Software Engineers</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="softwarearchitects.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="developer.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">Software Engineers using Enterprise Architect can map Use Cases onto <a href="classdiagram.htm">Class diagrams</a>, detail the interactions between Classes, define the system deployment with <a href="deploymentdiagram.htm">Deployment diagrams</a> and define software packages with <a href="packagediagram.htm">Package</a> diagrams.</span></p>
<p class="p_TextIndentedL2"><img src="example%20of%20a%20use%20case%20diagram2.png" width="760" height="350" border="0" alt="Example of a Use Case Diagram2"></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Map Use Cases into Detailed Classes</span></p>
<p class="p_BodyText"><span class="f_BodyText">In Enterprise Architect the Software Engineer can study the <a href="usecasediagram.htm">Use Cases</a> developed by the Software Architect, and with that information create Classes that fulfill the objectives defined in the Use Cases. A Class is one of the standard UML constructs that is used to detail the pattern from which objects are produced at run time. To record the relationships between Use Cases and Classes, the Software Engineer can create diagrams linking the elements with <a href="realise.htm">Realization</a> connectors, and/or map the Realization connectors in the <a href="elementrelationshipmatrix.htm">Relationship Matrix</a>.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Detail Interaction Between Classes</span></p>
<p class="p_BodyText"><span class="f_BodyText">Interaction diagrams (<a href="sequencediagram.htm">Sequence</a> and <a href="communicationdiagram.htm">Communication</a> diagrams) enable the Software Engineer to model the dynamic design of the system. Sequence diagrams are used to detail the messages passed between objects and the lifetimes of the objects. Communication diagrams are similar to Sequence diagrams, but are used instead to display the way in which objects interact with other objects.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Define System Deployment</span></p>
<p class="p_BodyText"><span class="f_Bulletlist1"><a href="deploymentdiagram.htm">Deployment diagrams</a></span><span class="f_BodyText"> can be used to provide a static view of the run-time configuration of processing nodes and the components that run on the nodes. Deployment diagrams can be used to show the connections between hardware, software and any middleware that is used on a system, to explain the connections and relationships of the components.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Define Software Packages</span></p>
<p class="p_BodyText"><span class="f_BodyText">The Software Engineer can use </span><span class="f_Bulletlist1"><a href="packagediagram.htm">Package diagrams</a></span><span class="f_BodyText"> to detail the software architecture. Package diagrams are used to organize diagrams and elements into manageable groups, declaring the dependencies.</span></p>
<p class="p_SeeAlso"><span class="f_SeeAlso">See Also</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1" style="font-style: italic;"><a href="uml.htm">Modeling with UML</a></span></li>
</ul>




            </div>
          </div>
        </div>



</div>


</body>
</html>
